-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wait until guest get IP in setup_dns #20261
Conversation
f7318e9
to
d93db72
Compare
d93db72
to
dffda9a
Compare
dffda9a
to
f0cd2c4
Compare
@alice-suse @waynechen55 @guoxuguang and others, welcome review! |
LGTM |
Thanks for the fix, Julie! I am not very familiar with this file logic, so will rely more on the file creator's review opinion. Anything fixing the issue is fine for me! |
@waynechen55 Would you please give priority to review this PR? We'd better have this before tomorrow's last alpha milestone candidate comes. |
get_vm_ipaddress=`tac $dhcpd_lease_file | awk '!($0 in S) {print; S[$0]}' | tac | grep -iE "${vm_macaddresses_array[${vm_hash_index}]}" -B8 | grep -oE "([0-9]{1,3}\.){3}[0-9]{1,3}" | tail -1` | ||
[[ -n "$vm_ipaddress" ]] && break | ||
sleep 10 | ||
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say that if guest gets ip address from internal dns service, it will not take so long to get a ip address. According to my observation, such guest can be fully up and running within 60 seconds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 tests always failed since sle15sp7:
https://10.145.10.207/tests/15612775#next_previous
https://10.145.10.207/tests/15612782#next_previous
They spent more time in getting an IP with unknown reasons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How long do they need ? Is it this specific to SRIOV scenario (SRIOV attached network interface) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How long do they need ?
I reproduced before the long holiday, it took nearly 3 minutes if I recalled correctly... I am not quite certain about the exact time since it has been too long since then.
Is it this specific to SRIOV scenario (SRIOV attached network interface) ?
No, this module is ahead of SRIOV tests. It runs after downloading and restoring a guest disk.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this issue happens frequently, is really significant and does not happen to other machines, I think you can do comparison with/out SRIOV settings ??? Or it only happens to certain machines regardless of SRIOV ???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW @waynechen55 , how do you suggest to go for this PR now? Merge it and you debug separately to have sooner milestone result, or not merge it and wait for a potential new solution by you?
I think I gave my opinions clearly, but I do not mind doing it again.
I think it worth having a look because test run on a network SR-IOV enabled host. You can still have a deeper look with this pull request in place when there is resource.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setup_dns has been always running on SR-IOV enabled host for a long time ... If you think there is a bug or problem on sle15sp7 in setup_dns, it will be good that you can open a bug. but for sriov passthrough tests to guest, I did not find a bug so far.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I think it worth having a look because test run on a network SR-IOV enabled host. You can still have a deeper look with this pull request in place when there is resource. I am happy if you confirm there is no issue at the moment or in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I will only take care of sriov test failure. About setup_dns problems, such as why the guest gets its IP longer than sle15sp6, it is beyond my knowledge and out of my fields.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. You can intervene test run manually and try boot vm manually on your SR-IOV enabled host to have a deeper look at this issue in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ignore this comment. Anyone can help delete this comment is better.
With offline confirmation, let's merge it now to unblock test first, and then investigate further. |
Related ticket: https://progress.opensuse.org/issues/167569
lsb_release
command in test script, becauseVerification run:
sriov_pci_passthrough-guest_developing_fv-on-host_developing-xen
sriov_pci_passthrough-guest_sles15sp6_fv-on-host_developing-xen
gi-guest_developing-on-host_developing-kvm
gi-guest_win2022-on-host_developing-xen